To
begin with, note that all users on Exchange 2000/2003 Mailbox Servers
are easily located within the Exchange Management Console. To see this,
perform the following:
1. | Open
the Exchange Management Console on an Exchange 2007 server (or from
another system that has the Exchange 2007 management tools installed).
|
2. | In the console tree, locate and select the Recipient Configuration node.
|
3. | Note
that next to the names of users, there is a column titled Recipient
Type Details that indicates whether a user is a legacy user, meaning
the user has a mailbox on a legacy Exchange server, or whether the user
is simply a user, as shown in Figure 1.
|
To
move a mailbox or multiple mailboxes in the same forest, you can use
the Move-Mailbox wizard from within the Exchange Management Console.
You can also use the Move-Mailbox cmdlet from within PowerShell.
To use the Exchange Management Console to move a mailbox or collection of mailboxes, perform the following:
1. | Open
the Exchange Management Console on an Exchange 2007 server (or from
another system that has the Exchange 2007 management tools installed).
|
2. | In the console tree, locate and select the Recipient Configuration node.
|
3. | Select the mailbox or mailboxes you wish to move.
|
4. | From the Actions Pane (or by right-clicking your selection), choose the Move Mailbox option and the wizard will begin.
|
5. | From
the Introduction screen, you have to select the Browse button and
choose the destination of the mailbox (to a different server or
different mailbox database on the same server). Then choose Next.
|
6. | Under the Move Options tab, shown in Figure 2,
you can choose what happens if corrupted messages are found. You can
skip the mailbox completely or you can skip the corrupted messages (and
determine the maximum number of messages to skip). You can usually just
skip corrupted messages because your goal is to move that mailbox over
for the transition, so you don’t have a choice—corrupted or not, that
mailbox has to move. You can personally select the
Global Catalog and Domain Controller for the move; if you don’t, the
wizard automatically handles this (and that is easiest and best). There
is also a checkbox for moving toward Exchange 2003 or 2000 (but we
aren’t doing that, so that option is unnecessary in this case). When
finished, click Next.
|
7. | You’re
taken to the Move Schedule tab, which enables you to move the mailbox
immediately, or at a time of your choosing (in the event you want to
wait until after work hours or the weekend, which is usually wise if
you are dealing with a production environment). Choose the date and
time and click Next.
|
8. | You
are presented with the Move Mailbox tab, which is a summary of your
entire request. It shows you all the mailboxes available for the move
and what options you’ve selected. If you feel it is ready, select Move.
|
9. | Ultimately
you end up on the Completion tab, where you are shown the results of
your requests to move the mailbox or mailboxes. Select Finish and you
should be set.
|
Using
the Exchange Management Shell can be slightly more complicated,
especially if you haven’t had experience with the shell or don’t prefer
the command-line approach. The wizard works just fine. However, if you
want to work with the move-mailbox cmdlet, you type in the following:
Move-Mailbox OrganizationName\UserName -TargetDatabase
“StorageGroupName\MailboxDatabaseName”
For
example, for an organization named PrimaTech that has a user, Jenny, to
move over to the UsersTwo Storage Group under the MBTwo Mailbox
Database, it would look like this:
Move-Mailbox PrimaTech\Jenny -TargetDatabase “UsersTwo\MBTwo”
For more cmdlet parameters, visit http://technet.microsoft.com/en-us/library/aa997961(EXCHG.80).aspx.
Note
You
cannot use the System Manager in Exchange to move mailboxes over to
Exchange 2007. It begins the process, and you can select the new
server, storage group, and database. However, the process fails because
Exchange 2003 doesn’t recognize this as a valid step.
